/lgtm

cc: @kubernetes/sig-api-machinery-leads for approve

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

It makes me sad that stuff like this doesn't get attention. Not only because this is about me specifically, but the wording here is so ironic - the bot starts by explaining that k8s doesn't have enough contributors, but resolving this (which seems to me like it should be a very quick review) is literally a way to help mitigate that very problem.

/remove-lifecycle stale

Ping @kubernetes/sig-api-machinery-leads

@tomasaschan: The label(s) /remove-label kind/api-change cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, ci-short, ci-extended, ci-full. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

@tomasaschan: Those labels are not set on the issue: api-review

Hey @mrbobbytables - did I do something wrong when I opened the PR? Like @tomasaschan I am surprised that this did not effectively merge-on-green

/lgtm
/approve

since it is open for months now

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justinsb, Priyankasaggu11929, tomasaschan

The full list of commands accepted by this bot can be found here.

The pull request process is described here